Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IMPROVE] Replace personalAccessTokens publication by REST #15644

Merged
merged 1 commit into from
Nov 5, 2019

Conversation

MarcosSpessatto
Copy link
Member

No description provided.

@@ -3,6 +3,7 @@ import { Meteor } from 'meteor/meteor';
import { hasPermission } from '../../../../app/authorization';
import { Users } from '../../../../app/models';

console.warn('The publication "personalAccessTokens" is deprecated and will be removed after version v3.0.0');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we move those warnings to inside the publication, so then we know when it has being used, today ir raises all those warnings on server startup what is not meaningful to understand if someplace is still using it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rodrigok That was a suggestion from @ggazzo and @sampaiodiego.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right.. this way (outside the publication) there is more chance of and admin to see the warning.

I would not mind adding to both places though. wdyt?

@sampaiodiego sampaiodiego merged commit 45b9e65 into develop Nov 5, 2019
@sampaiodiego sampaiodiego deleted the replace-personal-tokens-pub branch November 5, 2019 12:39
@sampaiodiego sampaiodiego mentioned this pull request Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants